Atmel ========== Release Notes ============= BitCloudTM 1_4_1 Date 02/17/2009 I. Scope ======== The purpose of the Release Notes is to specify the composition of BitCloudTM and system requirements. The known issues of this release are also described in this document. II. Products/configurations =========================== This package includes the following software products by Atmel and intended to run on Atmel hardware: - BitCloud stack 1.4.1 (headers and libraries); - sample application source files; - evaluation tool (WSN Monitor 1.9.7, SerialNet 2.1.0); III. Compatibility and minimum system requirements ================================================= PC CPU: Intel Pentium III or higher, 800 MHz RAM: 128 MB Hard disk free space: 50 MB Software Operating system: Windows 2000/XP Java machine: Java Runtime Environment, either JRE 5 Update 8 or more recent IV. Revision History =================== BitCloud 1.4.1: BitCloud Stack: --------------- All code was transferred to avr-gcc 4.3.2 compiler. Please, pay attention that the following GNU compiler (GCC) flags are used now: -mcall-prologues -fshort-enums. Take a look into GCC specification for details. #2640 ACTIVE_PERIOD parameter was removed from CS #2631 Time interval after which node's entry is removed from neighbor table is configurable now #2588 Address conflict indication was added BitCloud Stack bugs fixed: -------------------------- #2673 Pingpong - Coordinator doesn't update Neighbor table after 3 Link Status commands #2664 EndDevice sends Rejoin request and Data request from a new address, but Coordinator sends the old address in Rejoin response. #2657 Incorrect short address is returned in ZDO_MgmtNwkUpdateNotf() when indicating child leave #2625 A neighbor table entry that corresponds to coordinator has DEVICE_TYPE_ROUTER role #2616 ZdoNwkUpdateNtfy does not come after SetUserDescriptor #2610 Problem with MGMT_NWK_UPDATE_CLID zdp request on remote side #2605 New active channel shall be set to CS after it has been changed #2583 short PANID in received beacons is not checked during network formation #2575 APS doesn't clear tables' memory after reset #2573 CS parameters are not applied if SerialBootloader is used #2571 End device join shall consider link quality #2569 In network coordinator-end device, ZDO_CHILD_REMOVED_STATUS notification is never returned if end device is turned off. #2507 ED Scan does not work #2499 ZigBit doesn't have the 4MHz clock signal on the CPU_CLK (pin10) output #2426 I2c code does not correctly handle "Master Receiver Mode" of the TWI. #2407 Broadcast to FFFD addr is not done in correct way #2401 Zero extPANID instead of the Coordinator UID may be assumed by Coordinator #2360 Incorrect result of UID reading #2349 The first frame after RF reset has bad CRC #2202 Neighbours from other PANID are in LinkStatus command payload #2164 Coordinator sometimes performs a broadcast transmission to reserved addresses BitCloud 1.3.1: BitCloud Stack: --------------- #2648 AVR Studio project for Raven 3290P LCD controller was corrected. #2636 WSNDemo protocol description document was converted to Atmel application note format. BitCloud 1.3.0: BitCloud Stack: --------------- Support of RZRAVEN Kit was added. All code was transferred to avr-gcc 4.3.2 compiler. BitCloud 1.2.1: BitCloud Stack: --------------- #2548 Timer\Counter1 is free now. #2546 Support of VCP on ARM platform was added. #2498 RxOnWhenIdle, Relationship, PermitJoining, PotentialParent, Depth are additionally provided by ZDO_GetNeibTable(Neib_t * table ). #2519 Possibility to obtain real value of RF TX power was added. #2542, #2543 New persistent parameters were added CS_MANUFACTURER_CODE_ID - 16-bit manufacturer code allocated by the ZigBee Alliance CS_COMPLEX_DESCRIPTOR_AVAILABLE_ID - Specifies whether a complex descriptor is available on this device CS_USER_DESCRIPTOR_AVAILABLE_ID - Specifies whether a user descriptor is available on this device. #2547 Support of Alerton board was added. #2561 If feature commissioning is enabled then CS_NWK_PANID_ID parameter is stored to EEPROM. BitCloud Stack bugs fixed: -------------------------- #2555 Incorrect behaviour when broadcasting frames with radius larger than 0 was fixed. BitCloud 1.2.0: BitCloud Stack: --------------- Auto network feature was removed from stack and reimplemented on the application level. ZDP user descriptor support added. ZDO MGMT LQI request support added. Stack now provides a way for an application on coordinator to configure short PAN ID instead of generating it randomly. Stack enables correct work of the network consisting of 50 nodes. BitCloud Stack bugs fixed: -------------------------- Sometimes a router could freeze when working with indirect transactions. Unpredictable MAC confirmations could emerge during the MAC reset procedure. Broadcast data transmission reliability was about ~50%. A router joining to a secured network was incorrectly assigned a child status (instead of neighbor). Router did not send a new short address in rejoin response to a joining device whose short address was already contained in its neighbour table. A newly joining device with short address similar to one of those already contained in the neighbor table received secured rejoin response and thus was unable to join. Sometimes beacon was not sent after a beacon request. End device did not update its parent address. Application did not receive ZDO_SleepConf if an end device has lost the network. ZDP requests performed by a device locally (i.e. on itself) always failed on timeout. ZDO_GetNeibTable() could return non-empty table for a device with no neighbors. Performing an ED scan on a remote device always failed on timeout. Sample applications: -------------------- Autonetwork feature implemented BitCloud 1.1.1: BitCloud Stack features added: ------------------------------ When a coordinator with null CS_UID takes its extended PANID for CS_UID, it is not kept in persistent memory. Getting address of the first hop to certain destination. End device may go asleep when not joined to a network. ZDO_GetNeibAmount() and ZDO_GetNeibTable() functions added. BitCloud Stack bugs fixed: -------------------------- Fixed bug that hindered separate compilation for different node roles. Routers and end devices with AUTONETWORK option off could perform automatic rejoin. If an end device was reset while waiting for APS ack, it stopped further attempts to join the network. Coordinator took its COORDINATOR_EXT_PANID instead of CS_UID for MAC address on startup. Coordinator took null MAC address instead of CS_UID when starting network with null extended PANID. End device could not be put asleep by ZDO_SleepReq() function when not joined to a network. Sometimes APS ack was missing. APS_DataConf did not appear sometimes if a device has left the network. Incorrect battery status calculation. Asynchronous SPI mode was not available without rebuilding stack. Somatimes router did not process indirect transactions correctly. A node with invalid extended PANID sometimes appeared in beacon frame. PAN ID conflict resolution could lead to loss of nodes. End device incorrectly processed leave command received during rejoin procedure. Routers sometimes did not update capacity information for end devices. After sending leave request to an unexistent end device, router stopped answering all beacon requests. Coordinator occasionally sent Update device command to itself. Confirmation callback for ZDO_SetTxPowerReq() was never returned. V. Known issues and limitations ================================ BitCloud Stack -------------- Security is disabled for serial net. A device does not handle correctly receiving of two beacons in a row. Sometimes a device misses MAC acks and has to retransmit frames. VI. Technical Support ====================== Technical support is provided by Atmel Corporation: http://www.atmel.com email: avr@atmel.com